---
title: SAIF.Application.Claim configuration settings
summary: Configuration keys consumed by the claim-context application manager library, retrieval methods, and runtime dependencies.
status: draft
owner: SAIF Claims BOF team
last_reviewed: 2026-08-21
library: SAIF.Application.Claim
reference_type: embedded
---

# SAIF.Application.Claim configuration settings

`SAIF.Application.Claim` consumes exactly one configuration setting directly, retrieved via `IEnvironmentService.GetConfigSetting`, and registers one custom Oracle configuration section identically in `Web.config` and `app.config`. No `AppSettings`, secure/encrypted settings, or direct `DbConnectionManager` usage were found in this library's own scope.

## Configuration retrieval methods

| Method | Class / Interface | Namespace | Usage pattern |
| --- | --- | --- | --- |
| `GetConfigSetting(String)` | `EnvironmentService` (inherited member, `IEnvironmentService`-backed) | `SAIF.Core.Services`* | Called once, directly, inline in a read-only property getter to lazily construct a client object (`ClaimAppManager.ClaimImageApiClient`). |

## Environment API settings

Settings retrieved via `IEnvironmentService` (centralized environment configuration service).

| Setting key | Method | Data type | Purpose | Consuming class | Source |
| --- | --- | --- | --- | --- | --- |
| `imagingapiurl` | `GetConfigSetting` | String | Base URL/endpoint used to construct an `ImagingAPI.Client.ImagingClient` instance for claim image retrieval, based on the key name and its sole use as a client constructor argument* | `ClaimAppManager` | `SAIF.Application.Claim\ClaimAppManager.vb` |

This setting varies by environment: the key name and its sole usage as a client base-URL/endpoint argument indicate this is a service endpoint expected to differ across dev/test/staging/production environments*.

## AppSettings (Web.config)

None found. No `ConfigurationManager.AppSettings` calls were found in this library's source, and neither `Web.config` nor `app.config` declares an `<appSettings>` section.

## Database connection configuration

None found directly. Database connectivity is established indirectly through `DataLayer.CreateOraclePortal(ClaimAppConstants.DPIClaimKey)` (DPI key `"ClaimDPI"`) and `DataLayer.DBUser = "CLM"`, both members of `DataLayer` supplied by the `SAIF.Application` project reference and not re-documented here. No connection-string or `DbConnectionManager`-mediated key is declared within this library's own scope.

## Secure settings

None found. No `GetSecureConfigSetting` or `SystemHashUtil.ComputeHash` usage was found in this library's source.

## Custom configuration sections

| Section name | Handler type | Purpose |
| --- | --- | --- |
| `oracle.manageddataaccess.client` | `OracleInternal.Common.ODPMSectionHandler, Oracle.ManagedDataAccess, Version=4.122.21.1, Culture=neutral, PublicKeyToken=89b483f429c47342` | Configures the Oracle ODP.NET Managed Driver runtime (declared identically in both `Web.config` and `app.config`; no section content beyond the handler registration is present in either file)* |

Both `Web.config` and `app.config` also register a `<system.data><DbProviderFactories>` entry that removes and re-adds the `Oracle.ManagedDataAccess.Client` invariant, pointing at `Oracle.ManagedDataAccess.Client.OracleClientFactory` (same assembly/version as the section handler). This registers the Oracle provider factory used by ADO.NET provider-model code but is not itself a `<configSections>` custom section entry.

`app.config` additionally declares `<runtime><assemblyBinding>` binding redirects for `Newtonsoft.Json`, `System.Runtime.CompilerServices.Unsafe`, and `System.Text.Json` — standard assembly-version redirects, not application configuration settings.

## Transitive configuration (from dependencies)

Skipped — dependency resolution (`SAIF.Application` project reference and other same-repo/package dependencies) is out of scope for this configuration-focused analysis. `EnvironmentService`, `DataLayer`, and `AppManagerBase` are all inherited from the `SAIF.Application` project reference; any configuration keys those members consume internally are not cataloged here.

## Configuration dependencies

| Dependency | Type | Required at | Impact if missing |
| --- | --- | --- | --- |
| `imagingapiurl` | Environment API setting | Request (lazy, on first `ClaimImageApiClient` access) | `ImagingClient` construction would receive an empty/invalid base URL, likely causing imaging API calls to fail* |
| `oracle.manageddataaccess.client` config section | Custom configuration section | Startup | Oracle ODP.NET Managed Driver would not be correctly configured, likely preventing Oracle connectivity* |

## Configuration settings summary
- Total unique setting keys discovered: **1** (`imagingapiurl`, via `IEnvironmentService.GetConfigSetting`).
- Breakdown by retrieval method: `GetConfigSetting`: 1 key; `GetSecureConfigSetting`: 0; `ConfigurationManager.AppSettings`: 0; `DbConnectionManager`: 0 (indirect Oracle DPI context only, via inherited `DataLayer`).
- Secure/encrypted settings: 0.
- Custom configuration sections present: **1** (`oracle.manageddataaccess.client`).
- `ApplicationSettingsBase` settings: 0.

> **Note:** Statements marked with * were inferred from code structure, naming conventions, or
> contextual evidence where direct confirmation was not available in source artifacts. Statements
> marked with ** could not be confirmed; treat as unknown until verified.

## Related documentation
- [Library index](index.md)
- [Overview](overview.md)
- [Architecture](architecture.md)
- [Dependencies](dependencies.md)
- [Operations and processes](operations-processes.md)
- [Business rules](business-rules.md)
- [Security and authorization](security-authorization.md)
- [API reference](api/index.md)

## Sources
- `SAIF.Application.Claim\ClaimAppManager.vb`
- `SAIF.Application.Claim\Web.config`
- `SAIF.Application.Claim\app.config`